Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@pkg/cmd/ssl/create/create.go`:
- Line 159: The current code falls back to
cmdutil.NewExporter(...).WriteAPIResponse(body) when decoding api.SSL fails,
risking unredacted secret fields; change the control flow so that if decoding
api.SSL returns an error you do NOT call WriteAPIResponse(body) — instead
return/propagate the decode error (or send a generic error response) and only
call WriteAPIResponse after successfully decoding and applying api.RedactSSL on
the SSL struct; specifically, locate the branch where api.SSL is decoded and
replace the fallback to WriteAPIResponse(body) with error handling (or a
sanitized response) and ensure you call api.RedactSSL(&ssl) before any
serialization.

In `@pkg/cmd/ssl/update/update.go`:
- Line 182: The fallback path currently calls cmdutil.NewExporter(format,
out).WriteAPIResponse(body) which can export unredacted SSL secrets; update the
fallback to first call api.RedactSSL on the response payload (or construct a
redacted copy) and pass that redacted value to WriteAPIResponse so cert/key
material is never serialized, ensuring any SSL-bearing struct uses its
Redact/Marshal implementations; look for WriteAPIResponse, cmdutil.NewExporter,
and api.RedactSSL in the update handler and replace the direct
WriteAPIResponse(body) usage with a call that redacts (or converts to a redacted
struct) before exporting.

In `@pkg/cmdutil/exporter_test.go`:
- Line 1: This new Go test file is missing the project Apache 2.0 license
header; add the standard Apache 2.0 source header comment block at the very top
of the file above the existing "package cmdutil" declaration so the file begins
with the license header followed by the package statement, ensuring formatting
and year/owner placeholders follow the project's header template.

In `@pkg/cmdutil/exporter.go`:
- Around line 42-47: The Exporter.WriteAPIResponse currently uses json.Unmarshal
into an interface{}, which converts numbers to float64 and can lose precision;
change it to create a json.Decoder on an io.Reader (e.g.,
bytes.NewReader(body)), call decoder.UseNumber() before Decode(&decoded) so
numeric values are preserved as json.Number, then return e.Write(decoded) as
before; also add a unit test that sends a JSON payload with an integer > 2^53
through WriteAPIResponse and asserts the exported output preserves the exact
integer string to catch regressions.